Automate creation of the changelog after the release build#6742
Merged
Conversation
… verification and tagging this will create a PR with a changelog between tags. This also updates some plugin versions used in the release GitHub Action to the latest versions. Signed-off-by: David Venable <dlv@amazon.com>
dlvenable
requested review from
KarstenSchnitter,
dinujoh,
engechas,
graytaylor0,
kkondaka,
oeyh,
san81,
sb2k16 and
srikanthjg
as code owners
kkondaka
approved these changes
Apr 9, 2026
oeyh
approved these changes
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Generating the changelog for any release is a very straightforward task, but has been manual. This change generates it in the Release build.
After the verification and tagging this will generate the change log by using the latest tag and the tag of the version just released. It then creates a PR with the changelog.
Also I updated some plugin versions used in the release GitHub Action to the latest versions.
Testing
I ran this in my fork by simulating the 2.16 release.
Action run:
https://github.com/dlvenable/data-prepper/actions/runs/24058557223
Generated PR:
dlvenable#402
Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.